Mobile Number Switching: A mobile app can use this API to facilitate the process of switching mobile service providers for users. Users can enter their current subscriber number and the desired new service provider, and the app will handle the porting process using the tmf689 resourcePortability API interaction.
Bulk Porting: A business that wants to switch its entire workforce to a new service provider can use the tmf689 resourcePortability API to automate the porting process for all its employees. The company can input a list of subscriber numbers to be ported and track the progress of each request.
ListPortabilityOrder
Tracking Port Request Status Scenario: A telecom partner wants to track the status of a previously submitted Port Order request to ensure it is progressing as expected.
Resolving Port Request Issues Scenario: A telecom partner needs to resolve issues with a previously submitted Port Order request.
Auditing Port Requests Scenario: A telecom partner wants to audit their port requests to ensure compliance with industry standards and internal policies.
Generating Port Request Reports Scenario: A telecom partner wants to generate a report of all submitted Port Order requests to analyze their performance.
RetrievePortabilityActivationOrderById
New Subscriber Port Activation Tracking Scenario: A customer wants to port their existing phone number to a new service provider. The partner submits an Port Order request to begin the process and uses the RetrievePortabilityActivationOrderById API to track the progress of the port activation, ensuring a smooth transition for the customer.
Business Account Port Activation Management Scenario: A company is switching to a new service provider for their employees' mobile services and needs to port multiple phone numbers. The partner uses the RetrievePortabilityActivationOrderById API to monitor the status of each Port Order request, managing the activation process for all employees efficiently.
Troubleshooting Port Activation Issues Scenario: A customer encounters issues during the port activation process. The partner uses the RetrievePortabilityActivationOrderById API to identify the current status of the Port Order request and resolve any problems or delays, providing timely support and assistance to the customer.
Port Activation Reporting Scenario: A partner wants to generate a report on the status of all ongoing port activations for their customers. The partner uses the RetrievePortabilityActivationOrderById API to gather the necessary data and create a comprehensive report, helping to optimize their service and identify any potential bottlenecks in the process.
Port Activation Notifications Scenario: A customer wants to be notified when their port activation is complete. The partner uses the RetrievePortabilityActivationOrderById API to monitor the status of the Port Order request, and once the activation is successful, sends a notification to the customer informing them that their new service is active.
Coordinating Service Activation Scenario: A partner needs to coordinate the activation of additional services or features (e.g., voicemail, data plans) with the completion of the port activation process. The partner uses the RetrievePortabilityActivationOrderById API to determine when the port activation is successful, allowing them to proceed with the activation of the additional services.
PatchPortabilityOrder
Correcting Port Request Errors Scenario: A partner discovers an error in a previously submitted Port Order request, such as incorrect customer information or an invalid phone number. The partner uses the PatchPotabilityOrder API to modify the necessary details, ensuring the port activation process proceeds smoothly.
Updating Port Activation Dates Scenario: A customer requests to change the activation date for their port request due to personal circumstances or scheduling conflicts. The partner uses the PatchPotabilityOrder API to adjust the activation date, accommodating the customer's needs and providing flexibility in the process.
Addressing Port Activation Issues Scenario: A port activation process encounters difficulties or delays, and the partner identifies the issue as a problem with the original port request. The partner uses the PatchPotabilityOrder API to modify the necessary information, resolving the issue and allowing the port activation process to continue.
Multiple Number Port Request Modifications Scenario: A company needs to change information for several phone numbers in a single port request due to errors or updates in employee information. The partner uses the PatchPotabilityOrder API to make the necessary adjustments, streamlining the process and ensuring a successful port activation for all numbers involved.
createCancelPortabilityOrder
Incorrect Port In Request Scenario: A client submits an Port Order request to port in an existing subscriber from another service provider, but later realizes that they have provided incorrect information during the submission process. The client can use the createCancelPotabilityOrder API to cancel the outstanding port in request and prevent further processing.
Subscriber Changes Mind Scenario: A subscriber requests to port their number to a new service provider but later decides to stay with their current provider. In this case, the client can use the createCancelPotabilityOrder API to cancel the port in request, ensuring that the subscriber's number remains with their existing provider.
Incompatible Service Plan Scenario: A client submits a Port Order request to port in a subscriber from another service provider but later discovers that the subscriber's existing service plan is not compatible with their new provider's offerings. The client can use the createCancelPotabilityOrder API to cancel the outstanding port in request and avoid potential issues.
Failed Port In Attempts Scenario: A client has made several attempts to port in a subscriber from another service provider, but each attempt has resulted in errors or failures. After exhausting all possible solutions, the client can use the createCancelPotabilityOrder API to cancel the outstanding port in request and terminate the process.
Time Sensitive Cancellation Scenario: A client submits an Port Order request to port in a subscriber from another service provider, but the subscriber has a time-sensitive need to maintain their current service. The client can use the createCancelPotabilityOrder API to cancel the port in request and ensure the subscriber's service is not disrupted.
Compliance with Regulatory Requirements Scenario: A client submits an Port Order request to port in a subscriber from another service provider, but later receives information that the port in process might not be compliant with regulatory requirements. The client can use the createCancelPotabilityOrder API to cancel the outstanding port in request and maintain compliance.